Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a0cd7470abc332b0cf1e6e15286993c270821d61b8ebf61c24c4333fbe52cee

Tx prefix hash: 63f5d73e01719551cf33cc35fe1b74b144894dfe644365cc808b9acaf082eb9c
Tx public key: 9ca853ec9b89eba7b52fb76364886c8487dd67b1a2153e4c5f5af3989ab03d2c
Timestamp: 1731956164 Timestamp [UCT]: 2024-11-18 18:56:04 Age [y:d:h:m:s]: 00:136:06:08:49
Block: 1156576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97208 RingCT/type: yes/0
Extra: 019ca853ec9b89eba7b52fb76364886c8487dd67b1a2153e4c5f5af3989ab03d2c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c146e7f40f0561f55f0a323d7f3a07e31c19d4b799a9c705539e14213f9c14b 0.600000000000 1642199 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": 1156586, "vin": [ { "gen": { "height": 1156576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c146e7f40f0561f55f0a323d7f3a07e31c19d4b799a9c705539e14213f9c14b" } } ], "extra": [ 1, 156, 168, 83, 236, 155, 137, 235, 167, 181, 47, 183, 99, 100, 136, 108, 132, 135, 221, 103, 177, 162, 21, 62, 76, 95, 90, 243, 152, 154, 176, 61, 44, 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