Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b3cd264e63d0f89e5e342936dab000056782a9070a80c0a53fd2e8fb4bf4f51

Tx prefix hash: 83a86f3dd88cd926849daa530db2037e0d01f68c8d0f206bf0e57fab8d2a41d0
Tx public key: d851ae8f260d221b377b3f83441a7806a2e5299df6b63381e5bc3eee763b96b2
Timestamp: 1742036170 Timestamp [UTC]: 2025-03-15 10:56:10 Age [y:d:h:m:s]: 01:249:18:39:13
Block: 1239799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442634 RingCT/type: yes/0
Extra: 01d851ae8f260d221b377b3f83441a7806a2e5299df6b63381e5bc3eee763b96b20211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 017a5ff2c933bf1214e93cf38c0573d0e54d198cd03e8ba7b6fc17f2cca2864b 0.000600000000 1726764 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": 1239809, "vin": [ { "gen": { "height": 1239799 } } ], "vout": [ { "amount": 600000000, "target": { "key": "017a5ff2c933bf1214e93cf38c0573d0e54d198cd03e8ba7b6fc17f2cca2864b" } } ], "extra": [ 1, 216, 81, 174, 143, 38, 13, 34, 27, 55, 123, 63, 131, 68, 26, 120, 6, 162, 229, 41, 157, 246, 182, 51, 129, 229, 188, 62, 238, 118, 59, 150, 178, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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: