Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c97eeffa08677d4d64a7e891cc06d595876d8b641891973d140d816ae533d654

Tx prefix hash: e3b00d5f3ec6eb7d8a643ac04ccbe9263e1e24d45baf48028b7afa4cf9b4783c
Tx public key: bf5110c97b57c84448db74de2e11528fdf6320c635274f3b9acd8edc12224a70
Timestamp: 1698366423 Timestamp [UCT]: 2023-10-27 00:27:03 Age [y:d:h:m:s]: 01:165:09:01:43
Block: 878426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379185 RingCT/type: yes/0
Extra: 01bf5110c97b57c84448db74de2e11528fdf6320c635274f3b9acd8edc12224a7002110000000533af99f4000000000000000000

1 output(s) for total of 0.754067156000 dcy

stealth address amount amount idx
00: ca8ec19e4c0178ac3e64c82610aa145cc8ee8e7a51d5d4f2779a1b8c41524405 0.754067156000 1333868 of 0

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": 878436, "vin": [ { "gen": { "height": 878426 } } ], "vout": [ { "amount": 754067156, "target": { "key": "ca8ec19e4c0178ac3e64c82610aa145cc8ee8e7a51d5d4f2779a1b8c41524405" } } ], "extra": [ 1, 191, 81, 16, 201, 123, 87, 200, 68, 72, 219, 116, 222, 46, 17, 82, 143, 223, 99, 32, 198, 53, 39, 79, 59, 154, 205, 142, 220, 18, 34, 74, 112, 2, 17, 0, 0, 0, 5, 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