Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d289640dc2f2a3de197f3e2af7b92953cb2a8a945effdbe91f351284f60c2f49

Tx prefix hash: 1bf9b050414d084f9249f82379581d9c0d10c65efde1e4fdcad7088b775fb81a
Tx public key: 73c941db307fccdb190eab45820a90650f0c6de8bcf7a3e52d8e77775dd3eae9
Timestamp: 1737608723 Timestamp [UTC]: 2025-01-23 05:05:23 Age [y:d:h:m:s]: 01:297:12:57:04
Block: 1203346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476468 RingCT/type: yes/0
Extra: 0173c941db307fccdb190eab45820a90650f0c6de8bcf7a3e52d8e77775dd3eae9021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bfa48694e5216f6374c11a6350b99f78bad829036d7f4813246b4e4ea4ea6999 0.000600000000 1690023 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1203356, "vin": [ { "gen": { "height": 1203346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfa48694e5216f6374c11a6350b99f78bad829036d7f4813246b4e4ea4ea6999" } } ], "extra": [ 1, 115, 201, 65, 219, 48, 127, 204, 219, 25, 14, 171, 69, 130, 10, 144, 101, 15, 12, 109, 232, 188, 247, 163, 229, 45, 142, 119, 119, 93, 211, 234, 233, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: