Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dca602d9498a256ad8ae921f17b8d14218463603886577b2075a86fc62c46cbf

Tx prefix hash: 7cc3f924a5cfc13c33c64b4bfb5b7e5b8b03d1ef3cb2d40613e04688d712ed2e
Tx public key: 06e03f7962076778dbad20b3afa86898fc1bbc1a15ed44861ea1ae9b1c6027e6
Timestamp: 1720373402 Timestamp [UCT]: 2024-07-07 17:30:02 Age [y:d:h:m:s]: 01:129:06:28:13
Block: 1060647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350930 RingCT/type: yes/0
Extra: 0106e03f7962076778dbad20b3afa86898fc1bbc1a15ed44861ea1ae9b1c6027e602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 858711548efeaa7ca5cade9e99b28f3cfa91796b10c56a8a23898cdde07784a0 0.600000000000 1531132 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": 1060657, "vin": [ { "gen": { "height": 1060647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "858711548efeaa7ca5cade9e99b28f3cfa91796b10c56a8a23898cdde07784a0" } } ], "extra": [ 1, 6, 224, 63, 121, 98, 7, 103, 120, 219, 173, 32, 179, 175, 168, 104, 152, 252, 27, 188, 26, 21, 237, 68, 134, 30, 161, 174, 155, 28, 96, 39, 230, 2, 17, 0, 0, 0, 10, 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