Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025648ee1b5636209a55e3c0caca1042d2e4ea9315003b9e193fa3be3a393bac

Tx prefix hash: d2d164221ffd1dbbffe4282e912804f4d93f7b018c343de335de3f2682db6382
Tx public key: eedf844d55c8e7ac1ce0df71bcc7a96255d886890a308e5e1550a8f98bc9a1d9
Timestamp: 1580721111 Timestamp [UCT]: 2020-02-03 09:11:51 Age [y:d:h:m:s]: 04:301:00:43:38
Block: 57847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106345 RingCT/type: yes/0
Extra: 01eedf844d55c8e7ac1ce0df71bcc7a96255d886890a308e5e1550a8f98bc9a1d90211000000064ac5aa02000000000000000000

1 output(s) for total of 395.317330209000 dcy

stealth address amount amount idx
00: 99fc071cdbe4b5b8b13779e48ffbf1c8c31004f4c0e9ec7e980639651652322a 395.317330209000 106945 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": 57857, "vin": [ { "gen": { "height": 57847 } } ], "vout": [ { "amount": 395317330209, "target": { "key": "99fc071cdbe4b5b8b13779e48ffbf1c8c31004f4c0e9ec7e980639651652322a" } } ], "extra": [ 1, 238, 223, 132, 77, 85, 200, 231, 172, 28, 224, 223, 113, 188, 199, 169, 98, 85, 216, 134, 137, 10, 48, 142, 94, 21, 80, 168, 249, 139, 201, 161, 217, 2, 17, 0, 0, 0, 6, 74, 197, 170, 2, 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