Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d185b47050cc8f0172e8b4577ea42e26bcdce3195b4c58906224b85e65e4b33

Tx prefix hash: b54e18496a548c3d8589eeac2ef89ab3fa3653e63f523b4d361f4abe98b976ae
Tx public key: 50a33e8581c2a6ada2e5f7ad19ed2a0ac7e954b95e663985b82bf862ebfedb0a
Timestamp: 1700231976 Timestamp [UCT]: 2023-11-17 14:39:36 Age [y:d:h:m:s]: 01:142:16:52:54
Block: 893673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363155 RingCT/type: yes/0
Extra: 0150a33e8581c2a6ada2e5f7ad19ed2a0ac7e954b95e663985b82bf862ebfedb0a021100000002faf35c9c000000000000000000

1 output(s) for total of 0.671259372000 dcy

stealth address amount amount idx
00: d8670507a2c09d2760430f0323a3ff1d0e32968737224111fbc075c5e6e1df4d 0.671259372000 1349856 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 dinasty-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": 893683, "vin": [ { "gen": { "height": 893673 } } ], "vout": [ { "amount": 671259372, "target": { "key": "d8670507a2c09d2760430f0323a3ff1d0e32968737224111fbc075c5e6e1df4d" } } ], "extra": [ 1, 80, 163, 62, 133, 129, 194, 166, 173, 162, 229, 247, 173, 25, 237, 42, 10, 199, 233, 84, 185, 94, 102, 57, 133, 184, 43, 248, 98, 235, 254, 219, 10, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8