Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56cfb847aaf7b1abc12baeee408a17784dc9d2290ab8aa5d92162fcfc161e0a

Tx prefix hash: 0814ee5a22460c7f588b25b9fff53734945459fd1d99e516dd80b9e3f12cd34d
Tx public key: 63f7a4fc6f99844db1206e75ecfd1b4deb8de6884b8c1933fac01df2e94e45c4
Timestamp: 1706041862 Timestamp [UCT]: 2024-01-23 20:31:02 Age [y:d:h:m:s]: 02:006:17:27:00
Block: 941810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524410 RingCT/type: yes/0
Extra: 0163f7a4fc6f99844db1206e75ecfd1b4deb8de6884b8c1933fac01df2e94e45c40211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fee387965e9843ce0a7fdb22681ad7ed222a430cac244af76ef7e9d70a6c608a 0.600000000000 1399966 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": 941820, "vin": [ { "gen": { "height": 941810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fee387965e9843ce0a7fdb22681ad7ed222a430cac244af76ef7e9d70a6c608a" } } ], "extra": [ 1, 99, 247, 164, 252, 111, 153, 132, 77, 177, 32, 110, 117, 236, 253, 27, 77, 235, 141, 230, 136, 75, 140, 25, 51, 250, 192, 29, 242, 233, 78, 69, 196, 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