Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471f4e5f1857e4bfb25b42ae4e6a0e62730de0b7b35f445a00e37577340308d1

Tx prefix hash: 37c8820a0ae6a0d551bba3234e93fa67b913a7e69d78de06e72163248344845f
Tx public key: 00aaaf924169946d94b2c4ae5d2e573cc6882fc00a1a7f7362ad9e76627ba002
Timestamp: 1729321054 Timestamp [UCT]: 2024-10-19 06:57:34 Age [y:d:h:m:s]: 00:169:08:37:24
Block: 1134827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120808 RingCT/type: yes/0
Extra: 0100aaaf924169946d94b2c4ae5d2e573cc6882fc00a1a7f7362ad9e76627ba0020211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b68432914970d81bc2752ee371964078ea9d67be3e40541782e839b420f71c79 0.600000000000 1618154 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": 1134837, "vin": [ { "gen": { "height": 1134827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b68432914970d81bc2752ee371964078ea9d67be3e40541782e839b420f71c79" } } ], "extra": [ 1, 0, 170, 175, 146, 65, 105, 148, 109, 148, 178, 196, 174, 93, 46, 87, 60, 198, 136, 47, 192, 10, 26, 127, 115, 98, 173, 158, 118, 98, 123, 160, 2, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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