Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594a8808290f2db228cfd9c24024f1ca509dd7c5a116686308b7f22f91d88a2a

Tx prefix hash: 194858f965066ca2f59b1037ec8d168ae396f70b0e278d1b363d266101581c55
Tx public key: ef64880df1ff943dccb5577e39f55854ef743a7971513ba0a1ed3d4336c9f7a5
Timestamp: 1731875788 Timestamp [UCT]: 2024-11-17 20:36:28 Age [y:d:h:m:s]: 00:178:17:47:37
Block: 1155927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127587 RingCT/type: yes/0
Extra: 01ef64880df1ff943dccb5577e39f55854ef743a7971513ba0a1ed3d4336c9f7a5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f3663a9358884e4580daea8fba161af2b3e348deeb4f5ec1dca37c02e952dd 0.600000000000 1641546 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": 1155937, "vin": [ { "gen": { "height": 1155927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f3663a9358884e4580daea8fba161af2b3e348deeb4f5ec1dca37c02e952dd" } } ], "extra": [ 1, 239, 100, 136, 13, 241, 255, 148, 61, 204, 181, 87, 126, 57, 245, 88, 84, 239, 116, 58, 121, 113, 81, 59, 160, 161, 237, 61, 67, 54, 201, 247, 165, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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