Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e17a74642251ebb090dfe0bcfb2eb3d85735b560e8dcbede99c4c00a74e91f6

Tx prefix hash: a016546d5fd9d7601b3ff4fe5a4f82ef910612dcd76f13dcd031d53b8997592d
Tx public key: 0191be9291421e46bc7e9827be8c1f96c362dfb0162fd849f961f00b2ef1da29
Timestamp: 1737994194 Timestamp [UCT]: 2025-01-27 16:09:54 Age [y:d:h:m:s]: 00:144:01:09:07
Block: 1206338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102855 RingCT/type: yes/0
Extra: 010191be9291421e46bc7e9827be8c1f96c362dfb0162fd849f961f00b2ef1da290211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb8da408826e96f5604f900b88317b0a37771dd803c4a7544729d33f3cbed552 0.600000000000 1693041 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": 1206348, "vin": [ { "gen": { "height": 1206338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb8da408826e96f5604f900b88317b0a37771dd803c4a7544729d33f3cbed552" } } ], "extra": [ 1, 1, 145, 190, 146, 145, 66, 30, 70, 188, 126, 152, 39, 190, 140, 31, 150, 195, 98, 223, 176, 22, 47, 216, 73, 249, 97, 240, 11, 46, 241, 218, 41, 2, 17, 0, 0, 0, 5, 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