Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc64e95967005ab85c7ab266ccf6d26e042c08a073cf85889c95c9e02323d943

Tx prefix hash: f99e65c1323427870c722a8877c0d423e138ea26635832357b832dfc35fee169
Tx public key: e8e2949637a087af85d3b469bc15fab638e0e2e565b6bf480cb3ffd2875b1496
Timestamp: 1703002807 Timestamp [UCT]: 2023-12-19 16:20:07 Age [y:d:h:m:s]: 01:128:15:25:06
Block: 916653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353068 RingCT/type: yes/0
Extra: 01e8e2949637a087af85d3b469bc15fab638e0e2e565b6bf480cb3ffd2875b1496021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ae614c26e069e54b8499c0594a040655b04098b78597072dc6d1a0f2b6d05c 0.600000000000 1374211 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": 916663, "vin": [ { "gen": { "height": 916653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ae614c26e069e54b8499c0594a040655b04098b78597072dc6d1a0f2b6d05c" } } ], "extra": [ 1, 232, 226, 148, 150, 55, 160, 135, 175, 133, 211, 180, 105, 188, 21, 250, 182, 56, 224, 226, 229, 101, 182, 191, 72, 12, 179, 255, 210, 135, 91, 20, 150, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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