Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c18f78c353fd61c7919f710b59ba6f3864ab77a7ac519c793898b6f71ace4575

Tx prefix hash: d7dadb406ff96653b74c251e18ab7b4c33683b3f24ae95ff167d575bc78470ca
Tx public key: 0f08eb4bfe9d936844ffcb92034682af3931da3dfba9631b1de77933f1ecd6d3
Timestamp: 1717175884 Timestamp [UCT]: 2024-05-31 17:18:04 Age [y:d:h:m:s]: 00:298:21:40:17
Block: 1034145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213596 RingCT/type: yes/0
Extra: 010f08eb4bfe9d936844ffcb92034682af3931da3dfba9631b1de77933f1ecd6d302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 299541fed39f2453ee538ed6c04a0b948e35a6d903c9fe0bf3056c9b9f1d8be7 0.600000000000 1502626 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": 1034155, "vin": [ { "gen": { "height": 1034145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "299541fed39f2453ee538ed6c04a0b948e35a6d903c9fe0bf3056c9b9f1d8be7" } } ], "extra": [ 1, 15, 8, 235, 75, 254, 157, 147, 104, 68, 255, 203, 146, 3, 70, 130, 175, 57, 49, 218, 61, 251, 169, 99, 27, 29, 231, 121, 51, 241, 236, 214, 211, 2, 17, 0, 0, 0, 2, 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