Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c97e08d6ef2154437ecd417a0b697454f87535e525581f7c8502c67554b7f739

Tx prefix hash: 9bced7a965f3b7a9a614392ea0575cd722ca5258ba4b1c43541893bf23e1ae8f
Tx public key: ed7e5d9dc5dbda2022dd3a07afe35015f2e1f6629e95706c40ca6be1dc7860ab
Timestamp: 1720706166 Timestamp [UCT]: 2024-07-11 13:56:06 Age [y:d:h:m:s]: 00:260:20:40:51
Block: 1063417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186362 RingCT/type: yes/0
Extra: 01ed7e5d9dc5dbda2022dd3a07afe35015f2e1f6629e95706c40ca6be1dc7860ab021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c7ad54ed8408862f7b87942e06f50eabbb71bdc673b32de5be785a43b42acac 0.600000000000 1533932 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": 1063427, "vin": [ { "gen": { "height": 1063417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c7ad54ed8408862f7b87942e06f50eabbb71bdc673b32de5be785a43b42acac" } } ], "extra": [ 1, 237, 126, 93, 157, 197, 219, 218, 32, 34, 221, 58, 7, 175, 227, 80, 21, 242, 225, 246, 98, 158, 149, 112, 108, 64, 202, 107, 225, 220, 120, 96, 171, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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