Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 137932a97328982fb3ab4ff0c7768a4e8ad43fc255086bf897ee7203a44c9242

Tx prefix hash: e74f4dd09e413dc47aecd47303aa6431e8a5bfa2929cac76b7f749c50c75b461
Tx public key: 20b455067dd2c72af803cac664e288d134a32f9f8f4ae4fa4240dd7bdf7ea874
Timestamp: 1729171798 Timestamp [UCT]: 2024-10-17 13:29:58 Age [y:d:h:m:s]: 00:180:16:57:36
Block: 1133597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128931 RingCT/type: yes/0
Extra: 0120b455067dd2c72af803cac664e288d134a32f9f8f4ae4fa4240dd7bdf7ea87402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f220e393ececd67fb758a708f86fa1ca7af0842d2547bd4ebe6a71d81080968 0.600000000000 1616764 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": 1133607, "vin": [ { "gen": { "height": 1133597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f220e393ececd67fb758a708f86fa1ca7af0842d2547bd4ebe6a71d81080968" } } ], "extra": [ 1, 32, 180, 85, 6, 125, 210, 199, 42, 248, 3, 202, 198, 100, 226, 136, 209, 52, 163, 47, 159, 143, 74, 228, 250, 66, 64, 221, 123, 223, 126, 168, 116, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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