Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdef5536cfda223eed0c5d03748ffde2c57f9588570bca850dedbf0c8169e69

Tx prefix hash: 992e1374d291b79f7970902e881b29876b12346566c57eb7ddf72745d5eadac7
Tx public key: 957891e985c273c743cceb46d8be0dba731fe3a7d88308d49d84ed1e9658c08c
Timestamp: 1732646381 Timestamp [UCT]: 2024-11-26 18:39:41 Age [y:d:h:m:s]: 00:132:23:54:00
Block: 1162303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94855 RingCT/type: yes/0
Extra: 01957891e985c273c743cceb46d8be0dba731fe3a7d88308d49d84ed1e9658c08c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b99f1bd9a4205f7ced6996be28751c71be9c089b8f260d01a19aa396ea7fd5b0 0.600000000000 1647958 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": 1162313, "vin": [ { "gen": { "height": 1162303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b99f1bd9a4205f7ced6996be28751c71be9c089b8f260d01a19aa396ea7fd5b0" } } ], "extra": [ 1, 149, 120, 145, 233, 133, 194, 115, 199, 67, 204, 235, 70, 216, 190, 13, 186, 115, 31, 227, 167, 216, 131, 8, 212, 157, 132, 237, 30, 150, 88, 192, 140, 2, 17, 0, 0, 0, 1, 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