Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 406f904fab2c0c55486bf4d5afd6ac1b819ddd88c3a7aa5936d9f6cd004e8bf9

Tx prefix hash: 8b82cde8198877d71242c3319da603cb367e9136a906c2f7218971c1a91f4ad1
Tx public key: 366aaabd5db34516e3c09d250111eb8da9ddad8a5bcd8b8b012afb90d61cdcf0
Timestamp: 1789246847 Timestamp [UTC]: 2026-09-12 21:00:47 Age [y:d:h:m:s]: 00:065:04:10:35
Block: 1634060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 45984 RingCT/type: yes/0
Extra: 01366aaabd5db34516e3c09d250111eb8da9ddad8a5bcd8b8b012afb90d61cdcf0

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b06efa277e06969cb0e60a1098886dc95b87566db21eca6f5c8cad142d99a57a 0.000600000000 2124090 of 15 <2f>

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": 1634070, "vin": [ { "gen": { "height": 1634060 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b06efa277e06969cb0e60a1098886dc95b87566db21eca6f5c8cad142d99a57a", "view_tag": "2f" } } } ], "extra": [ 1, 54, 106, 170, 189, 93, 179, 69, 22, 227, 192, 157, 37, 1, 17, 235, 141, 169, 221, 173, 138, 91, 205, 139, 139, 1, 42, 251, 144, 214, 28, 220, 240 ], "rct_signatures": { "type": 0 } }


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