Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5481c1b5740dac02a53d6fbc074ccf7aa9526bd286a79fe886e2976a6430dc34

Tx prefix hash: ec27df98d86e477365dce201601469d2a52bd1d5c060ba60081319cecd2b4d9a
Tx public key: bb34009ec2a62eefd4547727bc2e1163fd58290660b21a1c8fb142ab3a2fb734
Timestamp: 1764902022 Timestamp [UTC]: 2025-12-05 02:33:42 Age [y:d:h:m:s]: 00:074:19:39:38
Block: 1426699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53345 RingCT/type: yes/0
Extra: 01bb34009ec2a62eefd4547727bc2e1163fd58290660b21a1c8fb142ab3a2fb73402110000000670609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd97952b4f6a3761d45c70132a7594f0889105b97aa0bd731d2d5efb7ef3dc5d 0.000600000000 1915392 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": 1426709, "vin": [ { "gen": { "height": 1426699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd97952b4f6a3761d45c70132a7594f0889105b97aa0bd731d2d5efb7ef3dc5d" } } ], "extra": [ 1, 187, 52, 0, 158, 194, 166, 46, 239, 212, 84, 119, 39, 188, 46, 17, 99, 253, 88, 41, 6, 96, 178, 26, 28, 143, 177, 66, 171, 58, 47, 183, 52, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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) | dinastycoin version: tesla-369