Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb8be9ee08147c8a44d794d594d3283859c1be82e97c60d89f5f7b1ef34fa6e3

Tx prefix hash: f665cadab53db7bf7399965420ff850babc2f2d4789114b54c1edb96b5bd0bf9
Tx public key: f1ecaa8f267ac513d5fb486cd418db18786cec97a6c7857528c4c583c218bcaa
Timestamp: 1734727450 Timestamp [UCT]: 2024-12-20 20:44:10 Age [y:d:h:m:s]: 00:094:12:47:14
Block: 1179565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67316 RingCT/type: yes/0
Extra: 01f1ecaa8f267ac513d5fb486cd418db18786cec97a6c7857528c4c583c218bcaa0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3f5ed18121cb75870e2c2a44597a0f8935edb859e87b8ef5c1c40d678e7f40 0.600000000000 1665960 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": 1179575, "vin": [ { "gen": { "height": 1179565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3f5ed18121cb75870e2c2a44597a0f8935edb859e87b8ef5c1c40d678e7f40" } } ], "extra": [ 1, 241, 236, 170, 143, 38, 122, 197, 19, 213, 251, 72, 108, 212, 24, 219, 24, 120, 108, 236, 151, 166, 199, 133, 117, 40, 196, 197, 131, 194, 24, 188, 170, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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