Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d6a13225f6e809a8dfc1a710cb881a0d209501625e996b2fd386a1418d831c

Tx prefix hash: f9be9ac636cca11440a6bbdc62c72020dd6a1e17dd904d9f06942bfb224bcd22
Tx public key: 8dd916c965b1fadde3921d5f4ab208897b756b576615ccc43109cdccecde3f8f
Timestamp: 1722284048 Timestamp [UCT]: 2024-07-29 20:14:08 Age [y:d:h:m:s]: 00:238:03:06:19
Block: 1076489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170082 RingCT/type: yes/0
Extra: 018dd916c965b1fadde3921d5f4ab208897b756b576615ccc43109cdccecde3f8f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41aaa3b7e82baa427dc3cf2435b47e1103a23b31b81757b5ee729f1a23b891db 0.600000000000 1549026 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": 1076499, "vin": [ { "gen": { "height": 1076489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41aaa3b7e82baa427dc3cf2435b47e1103a23b31b81757b5ee729f1a23b891db" } } ], "extra": [ 1, 141, 217, 22, 201, 101, 177, 250, 221, 227, 146, 29, 95, 74, 178, 8, 137, 123, 117, 107, 87, 102, 21, 204, 196, 49, 9, 205, 204, 236, 222, 63, 143, 2, 17, 0, 0, 0, 2, 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