Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d29fd436151845fa56e89975f7c2f7b0b2ee94d50ada6932a181271640176e8

Tx prefix hash: b71c7cf38a53fbf342969040f4f6ed902fc32d4910339c1a00f94fdfed54f523
Tx public key: f8962e366be6cd275cf67d5ede43d7f9b6d9e22541d41086d98a71b1bf814f1d
Timestamp: 1705218418 Timestamp [UCT]: 2024-01-14 07:46:58 Age [y:d:h:m:s]: 01:084:05:58:08
Block: 934986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321307 RingCT/type: yes/0
Extra: 01f8962e366be6cd275cf67d5ede43d7f9b6d9e22541d41086d98a71b1bf814f1d0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed2014dc930896a8ed7c63985c6d1d2b0b3460580f776a50cd60ee7169c67b2 0.600000000000 1393002 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": 934996, "vin": [ { "gen": { "height": 934986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed2014dc930896a8ed7c63985c6d1d2b0b3460580f776a50cd60ee7169c67b2" } } ], "extra": [ 1, 248, 150, 46, 54, 107, 230, 205, 39, 92, 246, 125, 94, 222, 67, 215, 249, 182, 217, 226, 37, 65, 212, 16, 134, 217, 138, 113, 177, 191, 129, 79, 29, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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