Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51346eed860a9709253e4d5ff5cdd7f863d217f7e8dc60840aa280977baa75d2

Tx prefix hash: 3fd127e00ee54457ecc29d8ef5aeb1f80aefaaeb1815f73ce956055123b8a783
Tx public key: ddb678cdfab5de0c7f6bf3dfb61428ce29835cb06cf8c6f871c180a9984b3bf8
Timestamp: 1717204616 Timestamp [UCT]: 2024-06-01 01:16:56 Age [y:d:h:m:s]: 01:162:02:55:17
Block: 1034384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374452 RingCT/type: yes/0
Extra: 01ddb678cdfab5de0c7f6bf3dfb61428ce29835cb06cf8c6f871c180a9984b3bf802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a89c08d5e442c2a1b055388f7674e374d4a899f987eea0280067baeaa053f15 0.600000000000 1502891 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": 1034394, "vin": [ { "gen": { "height": 1034384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a89c08d5e442c2a1b055388f7674e374d4a899f987eea0280067baeaa053f15" } } ], "extra": [ 1, 221, 182, 120, 205, 250, 181, 222, 12, 127, 107, 243, 223, 182, 20, 40, 206, 41, 131, 92, 176, 108, 248, 198, 248, 113, 193, 128, 169, 152, 75, 59, 248, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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