Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b15963d315742fe0372771ec36c958872d84630877ad7dc79a2b19aa33898a

Tx prefix hash: 73fc3c69dbeaf1a246871a5c39488abf216ec3a75c9e4f7b664cc9732689f56d
Tx public key: 553e855e84d211814ce13a7ddd31e87399e2cdca46e0a1d743c6ea721e403949
Timestamp: 1768074029 Timestamp [UTC]: 2026-01-10 19:40:29 Age [y:d:h:m:s]: 00:037:06:04:27
Block: 1452987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 26447 RingCT/type: yes/0
Extra: 01553e855e84d211814ce13a7ddd31e87399e2cdca46e0a1d743c6ea721e40394902090000001a8970985800

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6c0914249317bfb3bd0eb49c2ded713851ed21d1254cfaf7e790ab03e409e4bb 0.000600000000 1942019 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": 1452997, "vin": [ { "gen": { "height": 1452987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c0914249317bfb3bd0eb49c2ded713851ed21d1254cfaf7e790ab03e409e4bb" } } ], "extra": [ 1, 85, 62, 133, 94, 132, 210, 17, 129, 76, 225, 58, 125, 221, 49, 232, 115, 153, 226, 205, 202, 70, 224, 161, 215, 67, 198, 234, 114, 30, 64, 57, 73, 2, 9, 0, 0, 0, 26, 137, 112, 152, 88, 0 ], "rct_signatures": { "type": 0 } }


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