Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e593351dcb3153ab45dd9936abe216099473d44ef84dc95e3ced6e4bd1feaf2

Tx prefix hash: d86335163882aba8493d8a4a0b3c1ed29193705b489570a49a29a56332b6e240
Tx public key: 7063f8e713a259edd0f8b6a94ba51f648ddf80ab02aa940b1e88a5cd3334f1c5
Timestamp: 1720065088 Timestamp [UCT]: 2024-07-04 03:51:28 Age [y:d:h:m:s]: 00:319:10:53:01
Block: 1058090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228293 RingCT/type: yes/0
Extra: 017063f8e713a259edd0f8b6a94ba51f648ddf80ab02aa940b1e88a5cd3334f1c50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a483b9c3ecc99303cd940e9a9a5fd2527bba3777d4fae50ae2c6193d0d0093f 0.600000000000 1528539 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": 1058100, "vin": [ { "gen": { "height": 1058090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a483b9c3ecc99303cd940e9a9a5fd2527bba3777d4fae50ae2c6193d0d0093f" } } ], "extra": [ 1, 112, 99, 248, 231, 19, 162, 89, 237, 208, 248, 182, 169, 75, 165, 31, 100, 141, 223, 128, 171, 2, 170, 148, 11, 30, 136, 165, 205, 51, 52, 241, 197, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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