Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd66802bb1dd446e47f7f23ff3fb25f0d93ad4766764470ca313c60e3a28b7ae

Tx prefix hash: c45a0fcb43f41dd6fcab2cb59508451df418faf52bed972b445bcc03bbcb61cb
Tx public key: 3d5f1a91abb52b108b234459f349a8ff5d08f6744423dc7df8afc04ce4fab5e6
Timestamp: 1581222561 Timestamp [UCT]: 2020-02-09 04:29:21 Age [y:d:h:m:s]: 04:322:05:04:39
Block: 61035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122468 RingCT/type: yes/0
Extra: 013d5f1a91abb52b108b234459f349a8ff5d08f6744423dc7df8afc04ce4fab5e602110000001d4ac5aa02000000000000000000

1 output(s) for total of 385.301731698000 dcy

stealth address amount amount idx
00: 1b30387255dcb57106ca59721a4c3eb00bbf88fd4f5e9ff7c9eaea9af79f4d3a 385.301731698000 112502 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": 61045, "vin": [ { "gen": { "height": 61035 } } ], "vout": [ { "amount": 385301731698, "target": { "key": "1b30387255dcb57106ca59721a4c3eb00bbf88fd4f5e9ff7c9eaea9af79f4d3a" } } ], "extra": [ 1, 61, 95, 26, 145, 171, 181, 43, 16, 139, 35, 68, 89, 243, 73, 168, 255, 93, 8, 246, 116, 68, 35, 220, 125, 248, 175, 192, 76, 228, 250, 181, 230, 2, 17, 0, 0, 0, 29, 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