Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a56662b15a47e44f33ef8e3cd310470659a67c73b379158f929e5e4828f7d5c1

Tx prefix hash: 029ad1e5b631a0866f482dc222b75dc815311f728e69a54d30b02eed9b7fbc9d
Tx public key: b74de9bce2f68c0654446334d302271296f3b0a01e047ceb8f42e44feb632e71
Timestamp: 1677408814 Timestamp [UCT]: 2023-02-26 10:53:34 Age [y:d:h:m:s]: 02:255:10:53:46
Block: 705335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701878 RingCT/type: yes/0
Extra: 01b74de9bce2f68c0654446334d302271296f3b0a01e047ceb8f42e44feb632e7102110000000583600029000000000000000000

1 output(s) for total of 2.824439340000 dcy

stealth address amount amount idx
00: eabf55f100ed66b7f4c9cd8d07166fad32a539531b89ca6419916838fd8334e2 2.824439340000 1149030 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": 705345, "vin": [ { "gen": { "height": 705335 } } ], "vout": [ { "amount": 2824439340, "target": { "key": "eabf55f100ed66b7f4c9cd8d07166fad32a539531b89ca6419916838fd8334e2" } } ], "extra": [ 1, 183, 77, 233, 188, 226, 246, 140, 6, 84, 68, 99, 52, 211, 2, 39, 18, 150, 243, 176, 160, 30, 4, 124, 235, 143, 66, 228, 79, 235, 99, 46, 113, 2, 17, 0, 0, 0, 5, 131, 96, 0, 41, 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