Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ba2e86b93d6e46363ec21deba6f236840f978f49bdd60f22b2d117c74fb949

Tx prefix hash: cf7a6bdbe94c7198a59481c5db44e952949fd46c9a9512c98989753446f780b2
Tx public key: d6a4e2805597208d6d294acf66b46f1c296df0c850cef13fb13dcb7144e8ab1b
Timestamp: 1772995352 Timestamp [UTC]: 2026-03-08 18:42:32 Age [y:d:h:m:s]: 00:257:08:23:05
Block: 1493542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189577 RingCT/type: yes/0
Extra: 01d6a4e2805597208d6d294acf66b46f1c296df0c850cef13fb13dcb7144e8ab1b021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c6505a74f60800e38aa2d9a885c85420faa302c64b955be7eba9d7c3b16ad9d8 0.000600000000 1983102 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": 1493552, "vin": [ { "gen": { "height": 1493542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6505a74f60800e38aa2d9a885c85420faa302c64b955be7eba9d7c3b16ad9d8" } } ], "extra": [ 1, 214, 164, 226, 128, 85, 151, 32, 141, 109, 41, 74, 207, 102, 180, 111, 28, 41, 109, 240, 200, 80, 206, 241, 63, 177, 61, 203, 113, 68, 232, 171, 27, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: