Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8f5c301be2055eca063b3541039a9337c865dd716f516c7903690272eab8f64

Tx prefix hash: 501370defe0cacdc2e2da32aaa92e0e9d065d0345e60ba2218ed6fc0b6158c60
Tx public key: e2ec9a7451bc5af3328e08b3b568177c6ec5922c2bd8fbf2fb3903f0717b9b38
Timestamp: 1729426674 Timestamp [UCT]: 2024-10-20 12:17:54 Age [y:d:h:m:s]: 00:239:06:52:23
Block: 1135702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170725 RingCT/type: yes/0
Extra: 01e2ec9a7451bc5af3328e08b3b568177c6ec5922c2bd8fbf2fb3903f0717b9b38021100000002a6b5e9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22bd3422b2a8f74b66eee257281c5b261be8acdb8da35f28494623ac385f62bc 0.600000000000 1619041 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": 1135712, "vin": [ { "gen": { "height": 1135702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22bd3422b2a8f74b66eee257281c5b261be8acdb8da35f28494623ac385f62bc" } } ], "extra": [ 1, 226, 236, 154, 116, 81, 188, 90, 243, 50, 142, 8, 179, 181, 104, 23, 124, 110, 197, 146, 44, 43, 216, 251, 242, 251, 57, 3, 240, 113, 123, 155, 56, 2, 17, 0, 0, 0, 2, 166, 181, 233, 251, 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