Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b7209e8811c1cb63b2c842b7936064f996da07555916be03877990845c9e260

Tx prefix hash: 96fe40c186bad4ae543cc355f789cbf8820aadabcb4f05d1e5efc7a097f21f3c
Tx public key: c5ccfe389d222e2343227f1a7376260ee19d0578d9e8188fd114c1f7cf14c92a
Timestamp: 1700393558 Timestamp [UCT]: 2023-11-19 11:32:38 Age [y:d:h:m:s]: 01:142:15:01:37
Block: 895007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363117 RingCT/type: yes/0
Extra: 01c5ccfe389d222e2343227f1a7376260ee19d0578d9e8188fd114c1f7cf14c92a02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.664472177000 dcy

stealth address amount amount idx
00: 268933fa501c7617e7c054973e2330c1a7266a646f36630d6868b4d8e5dd8f91 0.664472177000 1351226 of 0

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": 895017, "vin": [ { "gen": { "height": 895007 } } ], "vout": [ { "amount": 664472177, "target": { "key": "268933fa501c7617e7c054973e2330c1a7266a646f36630d6868b4d8e5dd8f91" } } ], "extra": [ 1, 197, 204, 254, 56, 157, 34, 46, 35, 67, 34, 127, 26, 115, 118, 38, 14, 225, 157, 5, 120, 217, 232, 24, 143, 209, 20, 193, 247, 207, 20, 201, 42, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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