Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 114f128d09ca76ad99d6ad37c6a7e47e4c5016a7fbed053b189679c09fb0390a

Tx prefix hash: 0671b18e097f9804e6a52d9310d44c8e585d828028d0543b29b545784ebbe56b
Tx public key: fe6c6f5c4dac0f7d2cad7cb2ef916e35e98ed3cd94aa6e9e71833636ad68e832
Timestamp: 1702587209 Timestamp [UCT]: 2023-12-14 20:53:29 Age [y:d:h:m:s]: 01:327:06:45:04
Block: 913181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492758 RingCT/type: yes/0
Extra: 01fe6c6f5c4dac0f7d2cad7cb2ef916e35e98ed3cd94aa6e9e71833636ad68e83202110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04a927a61e5978f9ae23a48e3f41465cf38a3fac760bdecd094fb5fd093a088f 0.600000000000 1370427 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": 913191, "vin": [ { "gen": { "height": 913181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04a927a61e5978f9ae23a48e3f41465cf38a3fac760bdecd094fb5fd093a088f" } } ], "extra": [ 1, 254, 108, 111, 92, 77, 172, 15, 125, 44, 173, 124, 178, 239, 145, 110, 53, 233, 142, 211, 205, 148, 170, 110, 158, 113, 131, 54, 54, 173, 104, 232, 50, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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