Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41d8002ffee3bdf0cd079fd739d0cf319af58a84d821aa39f43d30f53979ad7

Tx prefix hash: 2a542d5d29d5378efa45c4deee311137a9ea0e21f70bd6902c2b0d3b0e068320
Tx public key: 828a436886671174f2d0abbf2dfe3d7fde5993e62be9cea309c7e1343cc4f17e
Timestamp: 1647959516 Timestamp [UTC]: 2022-03-22 14:31:56 Age [y:d:h:m:s]: 04:049:20:13:15
Block: 464009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1067019 RingCT/type: yes/0
Extra: 01828a436886671174f2d0abbf2dfe3d7fde5993e62be9cea309c7e1343cc4f17e02110000000d06faf294000000000000000000

1 output(s) for total of 0.017805157593 xmr

stealth address amount amount idx tag
00: 14aa89265f4ddb54de57c3c51b4a3227c58c1b5ae2cb6ddf8616cd373e0db7e2 0.017805157593 881796 of 0 -

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": 464019, "vin": [ { "gen": { "height": 464009 } } ], "vout": [ { "amount": 17805157593, "target": { "key": "14aa89265f4ddb54de57c3c51b4a3227c58c1b5ae2cb6ddf8616cd373e0db7e2" } } ], "extra": [ 1, 130, 138, 67, 104, 134, 103, 17, 116, 242, 208, 171, 191, 45, 254, 61, 127, 222, 89, 147, 230, 43, 233, 206, 163, 9, 199, 225, 52, 60, 196, 241, 126, 2, 17, 0, 0, 0, 13, 6, 250, 242, 148, 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: