Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a51d01f0cf30582bb6c9b162045e639d4571525fdbfd7451f762486f9bc58e

Tx prefix hash: b0a9750f56f9f1f7bff4989adb533ee395d2b00671b0565fcf03cec9c0dfd892
Tx public key: 14cd370e65a5edcf2a45fe55e1488ccf9ee5e9f309bfab34ba04e6297b602d49
Timestamp: 1736674886 Timestamp [UCT]: 2025-01-12 09:41:26 Age [y:d:h:m:s]: 00:103:05:59:07
Block: 1195657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73587 RingCT/type: yes/0
Extra: 0114cd370e65a5edcf2a45fe55e1488ccf9ee5e9f309bfab34ba04e6297b602d490211000000121f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fffc970797b512f83bef10669d9cb789db36b207e79b2e80dd74c8e88a823cab 0.600000000000 1682248 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": 1195667, "vin": [ { "gen": { "height": 1195657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fffc970797b512f83bef10669d9cb789db36b207e79b2e80dd74c8e88a823cab" } } ], "extra": [ 1, 20, 205, 55, 14, 101, 165, 237, 207, 42, 69, 254, 85, 225, 72, 140, 207, 158, 229, 233, 243, 9, 191, 171, 52, 186, 4, 230, 41, 123, 96, 45, 73, 2, 17, 0, 0, 0, 18, 31, 10, 83, 235, 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