Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b888d14f45457d4c5099109973c4b0fbf7271d60817554eb10b4ba5e98ff87ac

Tx prefix hash: d5c20ccc5e76e99312941d7d43cf9ae940533c5157aa951b63a4151fbdec5696
Tx public key: 1e2194de2c5566d411e716f5e4b47f3b54991852e660528e302ff8bfa8fcff15
Timestamp: 1725463246 Timestamp [UCT]: 2024-09-04 15:20:46 Age [y:d:h:m:s]: 00:048:13:02:00
Block: 1102860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34728 RingCT/type: yes/0
Extra: 011e2194de2c5566d411e716f5e4b47f3b54991852e660528e302ff8bfa8fcff1502110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abac9b910f419579c64484a06c06a94850a4f8dec22fa0876e35fff2f8652fa9 0.600000000000 1579455 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": 1102870, "vin": [ { "gen": { "height": 1102860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abac9b910f419579c64484a06c06a94850a4f8dec22fa0876e35fff2f8652fa9" } } ], "extra": [ 1, 30, 33, 148, 222, 44, 85, 102, 212, 17, 231, 22, 245, 228, 180, 127, 59, 84, 153, 24, 82, 230, 96, 82, 142, 48, 47, 248, 191, 168, 252, 255, 21, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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