Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 889bd7fbe473b119d623cce588c6443798bc3c5b1c6fa4da7935b9299da1d359

Tx prefix hash: 7490cf83083c71cd420fad23163ba3311ec96ad57bc22611756f05a50b11a618
Tx public key: ec0585e7dc865c5a8501f2f297d8a21afd95e6f0f9c963d917bf4eb0d69c3f1d
Timestamp: 1702366028 Timestamp [UCT]: 2023-12-12 07:27:08 Age [y:d:h:m:s]: 01:117:23:08:57
Block: 911375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345421 RingCT/type: yes/0
Extra: 01ec0585e7dc865c5a8501f2f297d8a21afd95e6f0f9c963d917bf4eb0d69c3f1d02110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 587835825cbf5487a5177801073642367f13b38e9cd68c89fd0afe380e551408 0.600000000000 1368560 of 15

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": 911385, "vin": [ { "gen": { "height": 911375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "587835825cbf5487a5177801073642367f13b38e9cd68c89fd0afe380e551408" } } ], "extra": [ 1, 236, 5, 133, 231, 220, 134, 92, 90, 133, 1, 242, 242, 151, 216, 162, 26, 253, 149, 230, 240, 249, 201, 99, 217, 23, 191, 78, 176, 214, 156, 63, 29, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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