Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec9f737c851d334ec35c6a2ede2dd102005c87ab3a86609a53fb17719aa9fe68

Tx prefix hash: 4c3945dc154c07c52e2deb2b2bef225a99ac5d046dcc5f52ed44384e2b0cab12
Tx public key: 8e6c94b4e912ffade71c79a8b58f0adbbb63d2241fd295829954a5e6314ba5ec
Timestamp: 1709909207 Timestamp [UCT]: 2024-03-08 14:46:47 Age [y:d:h:m:s]: 01:013:10:20:44
Block: 973903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270591 RingCT/type: yes/0
Extra: 018e6c94b4e912ffade71c79a8b58f0adbbb63d2241fd295829954a5e6314ba5ec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c7d0f23e181df0d515a7bd1089552b9c3d8d943c50e2e6b56d2dcf684b1e34e 0.600000000000 1433846 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": 973913, "vin": [ { "gen": { "height": 973903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c7d0f23e181df0d515a7bd1089552b9c3d8d943c50e2e6b56d2dcf684b1e34e" } } ], "extra": [ 1, 142, 108, 148, 180, 233, 18, 255, 173, 231, 28, 121, 168, 181, 143, 10, 219, 187, 99, 210, 36, 31, 210, 149, 130, 153, 84, 165, 230, 49, 75, 165, 236, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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