Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 819160aa89657e5a475d1410a130dbcdacc16083f12e63b7129731a5edbec0ab

Tx prefix hash: 4f8f882134a619c538a3d4ea19e7a3c47d62447d9dbed57919dc403679a66848
Tx public key: d06def8ea60a8e425727f02d5b799343bad1c52f859ace1713ead9035b5fd91f
Timestamp: 1725144129 Timestamp [UCT]: 2024-08-31 22:42:09 Age [y:d:h:m:s]: 00:280:01:09:51
Block: 1100196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200053 RingCT/type: yes/0
Extra: 01d06def8ea60a8e425727f02d5b799343bad1c52f859ace1713ead9035b5fd91f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07428ab3bb8306aa6a819c9b00a47f19da67ae0ec55aea3f89610468fd44f624 0.600000000000 1576169 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": 1100206, "vin": [ { "gen": { "height": 1100196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07428ab3bb8306aa6a819c9b00a47f19da67ae0ec55aea3f89610468fd44f624" } } ], "extra": [ 1, 208, 109, 239, 142, 166, 10, 142, 66, 87, 39, 240, 45, 91, 121, 147, 67, 186, 209, 197, 47, 133, 154, 206, 23, 19, 234, 217, 3, 91, 95, 217, 31, 2, 17, 0, 0, 0, 5, 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