Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326d5c5faf51560f3afbc659b0df925de898f3691feb6f812442e7a7449fc337

Tx prefix hash: 7da83eec3edb0e4ce905e1c0a1bde37f5559a79e32ba39ad3c7dee562a0052d8
Tx public key: a4cc1149228e1df2757be61fe097d9d74f692d8ffb01124798d36a97c6439a3d
Timestamp: 1577413870 Timestamp [UTC]: 2019-12-27 02:31:10 Age [y:d:h:m:s]: 06:274:01:45:01
Block: 32570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1610451 RingCT/type: yes/0
Extra: 01a4cc1149228e1df2757be61fe097d9d74f692d8ffb01124798d36a97c6439a3d0211000000044943cd9f000000000000000000

1 output(s) for total of 0.478721494956 xmr

stealth address amount amount idx tag
00: e1d9ae75042541ca79fc7310c7aec136c39224a9738a1fe35534645e23ba000c 0.478721494956 54210 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": 32580, "vin": [ { "gen": { "height": 32570 } } ], "vout": [ { "amount": 478721494956, "target": { "key": "e1d9ae75042541ca79fc7310c7aec136c39224a9738a1fe35534645e23ba000c" } } ], "extra": [ 1, 164, 204, 17, 73, 34, 142, 29, 242, 117, 123, 230, 31, 224, 151, 217, 215, 79, 105, 45, 143, 251, 1, 18, 71, 152, 211, 106, 151, 198, 67, 154, 61, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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: