Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9566c29c16aa7f170f7a3df2b7be66b5f13d8034801a49cbe07acafd8e619a5c

Tx prefix hash: b49b3891c73dd01388160f74413d6d8b06db70bd741a0a55e8e7e04ee23aef1c
Tx public key: d0bc6678df03e310d8a84a325e727fba2b80128d1633e7308d7c7d5a178f3115
Timestamp: 1587792767 Timestamp [UCT]: 2020-04-25 05:32:47 Age [y:d:h:m:s]: 04:252:03:03:05
Block: 96093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091660 RingCT/type: yes/0
Extra: 01d0bc6678df03e310d8a84a325e727fba2b80128d1633e7308d7c7d5a178f3115021100000040d81c26c0000000000000000000

1 output(s) for total of 294.864028143000 dcy

stealth address amount amount idx
00: fded7416b385d9877fd81876ec01f7040202ecee87b39bd740a707bc3d8a38fa 294.864028143000 170516 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": 96103, "vin": [ { "gen": { "height": 96093 } } ], "vout": [ { "amount": 294864028143, "target": { "key": "fded7416b385d9877fd81876ec01f7040202ecee87b39bd740a707bc3d8a38fa" } } ], "extra": [ 1, 208, 188, 102, 120, 223, 3, 227, 16, 216, 168, 74, 50, 94, 114, 127, 186, 43, 128, 18, 141, 22, 51, 231, 48, 141, 124, 125, 90, 23, 143, 49, 21, 2, 17, 0, 0, 0, 64, 216, 28, 38, 192, 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