Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2d7c72b0caa3f3b90024a3a50f4d0a85de41c45a444beb39adb61a9ba9e664d

Tx prefix hash: 765c9974df75d281decdd0d2e7ec723ec6eea2482def79f423b68552600549ec
Tx public key: 277ec428e229141f21faacfd9823c1b34bdd95ec0030370bb74b67582e6ba85a
Timestamp: 1765823841 Timestamp [UTC]: 2025-12-15 18:37:21 Age [y:d:h:m:s]: 00:145:21:54:23
Block: 1434317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96891 RingCT/type: yes/0
Extra: 01277ec428e229141f21faacfd9823c1b34bdd95ec0030370bb74b67582e6ba85a021100000008d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8f0d630bebba36beaf0e7a5117cdafa85ae395093e1a3aa22d4fb71bc3d507ae 0.000600000000 1923106 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": 1434327, "vin": [ { "gen": { "height": 1434317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f0d630bebba36beaf0e7a5117cdafa85ae395093e1a3aa22d4fb71bc3d507ae" } } ], "extra": [ 1, 39, 126, 196, 40, 226, 41, 20, 31, 33, 250, 172, 253, 152, 35, 193, 179, 75, 221, 149, 236, 0, 48, 55, 11, 183, 75, 103, 88, 46, 107, 168, 90, 2, 17, 0, 0, 0, 8, 214, 225, 157, 124, 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: