Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5078ea4b3ed127734903830ed3a13f5aacda85dc889d2731964da6f4ce947e8f

Tx prefix hash: 93726e9c30b5297d1269276fcc7b5bfd4c2cd3595bfd1f74ada1941a273cb194
Tx public key: 16898b7f587c34e55e4ea2441b9d5246e8b16c7c0a33a24fdf7bbe32f567e365
Timestamp: 1577696981 Timestamp [UCT]: 2019-12-30 09:09:41 Age [y:d:h:m:s]: 05:000:02:32:47
Block: 34896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150090 RingCT/type: yes/0
Extra: 0116898b7f587c34e55e4ea2441b9d5246e8b16c7c0a33a24fdf7bbe32f567e365021100000007d81c26c0000000000000000000

1 output(s) for total of 470.380400474000 dcy

stealth address amount amount idx
00: ad8113806a5e40795cc2b4c8842f9af8d059171127196305d970339d16777f47 470.380400474000 58789 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": 34906, "vin": [ { "gen": { "height": 34896 } } ], "vout": [ { "amount": 470380400474, "target": { "key": "ad8113806a5e40795cc2b4c8842f9af8d059171127196305d970339d16777f47" } } ], "extra": [ 1, 22, 137, 139, 127, 88, 124, 52, 229, 94, 78, 162, 68, 27, 157, 82, 70, 232, 177, 108, 124, 10, 51, 162, 79, 223, 123, 190, 50, 245, 103, 227, 101, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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