Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8eb672dc09cc80d243ebba0ccb5d189cc938ff1e6b99819259cc564aed77656a

Tx prefix hash: 12a4d6ecc936fae8e869235d25a60f721c830366366c2d1814d798f76dac01f3
Tx public key: b8e44291dcab65883c8d2eab01d655ef8e2bd642849d3b781629c6c3d903f7c3
Timestamp: 1708488605 Timestamp [UCT]: 2024-02-21 04:10:05 Age [y:d:h:m:s]: 01:049:18:52:24
Block: 962118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296608 RingCT/type: yes/0
Extra: 01b8e44291dcab65883c8d2eab01d655ef8e2bd642849d3b781629c6c3d903f7c302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1edf478f05d8cd20cc08bc01ece7482177b444d2aa3d4f31c893217f78dc762b 0.600000000000 1421741 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": 962128, "vin": [ { "gen": { "height": 962118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1edf478f05d8cd20cc08bc01ece7482177b444d2aa3d4f31c893217f78dc762b" } } ], "extra": [ 1, 184, 228, 66, 145, 220, 171, 101, 136, 60, 141, 46, 171, 1, 214, 85, 239, 142, 43, 214, 66, 132, 157, 59, 120, 22, 41, 198, 195, 217, 3, 247, 195, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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