Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96a5be5498c32e31c6d0e0fb717ac2a714f8b3260c549f8586dc08a8ace4488

Tx prefix hash: e7f33a9c60a88c9f07311b7c56eb7ce5a9ad7c978ca988fa7ee67f2622c7869b
Tx public key: 4f7075880be51a721732c2e8a6cfa9a8fc8dfeabc25a1b8d6b020d10f5cf03e2
Timestamp: 1706377619 Timestamp [UCT]: 2024-01-27 17:46:59 Age [y:d:h:m:s]: 01:098:09:10:23
Block: 944596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331412 RingCT/type: yes/0
Extra: 014f7075880be51a721732c2e8a6cfa9a8fc8dfeabc25a1b8d6b020d10f5cf03e20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e3090fbc1f74380008684535af3edc9b4362eb5fcee089ec59bac5df721938b 0.600000000000 1402878 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": 944606, "vin": [ { "gen": { "height": 944596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e3090fbc1f74380008684535af3edc9b4362eb5fcee089ec59bac5df721938b" } } ], "extra": [ 1, 79, 112, 117, 136, 11, 229, 26, 114, 23, 50, 194, 232, 166, 207, 169, 168, 252, 141, 254, 171, 194, 90, 27, 141, 107, 2, 13, 16, 245, 207, 3, 226, 2, 17, 0, 0, 0, 2, 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