Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae74d14f70998b9411ba4da788e2e874c5cbae988616c673df4bc37f0936d2d3

Tx prefix hash: 1953d7a81a2bd3f43af75224ce6afb6c3ac79a8d13cc8296af592007522e672a
Tx public key: da88c63c738f41d0ad3a63dfa80fa25cee0abe6ca4e8b302b5aa74cae09c867f
Timestamp: 1705999751 Timestamp [UCT]: 2024-01-23 08:49:11 Age [y:d:h:m:s]: 01:151:13:59:02
Block: 941456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369281 RingCT/type: yes/0
Extra: 01da88c63c738f41d0ad3a63dfa80fa25cee0abe6ca4e8b302b5aa74cae09c867f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e8ad4a0114f9596970bb473e4e20317d6e35de5f633b561ac98b65103685d3d 0.600000000000 1399606 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": 941466, "vin": [ { "gen": { "height": 941456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e8ad4a0114f9596970bb473e4e20317d6e35de5f633b561ac98b65103685d3d" } } ], "extra": [ 1, 218, 136, 198, 60, 115, 143, 65, 208, 173, 58, 99, 223, 168, 15, 162, 92, 238, 10, 190, 108, 164, 232, 179, 2, 181, 170, 116, 202, 224, 156, 134, 127, 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