Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe77f777ceda7f56c4348cebe567f733bbe2791fa534b80f9a2e3deb50c31a7b

Tx prefix hash: 65f5a4c2d81374b3121e67637269d76558b832a1fb86690b14eb0a5c20af7133
Tx public key: 7b3c9e4d348fb23a62991d9a2b663b8eec2ef7c253d9808d0b4c5ad2f13dfd94
Timestamp: 1707723349 Timestamp [UCT]: 2024-02-12 07:35:49 Age [y:d:h:m:s]: 01:093:14:14:25
Block: 955771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327959 RingCT/type: yes/0
Extra: 017b3c9e4d348fb23a62991d9a2b663b8eec2ef7c253d9808d0b4c5ad2f13dfd940211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f050dc66037781f8782aa15bcebd0dd8f04cc2db0ea2ba9e2659097469900cc9 0.600000000000 1415071 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": 955781, "vin": [ { "gen": { "height": 955771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f050dc66037781f8782aa15bcebd0dd8f04cc2db0ea2ba9e2659097469900cc9" } } ], "extra": [ 1, 123, 60, 158, 77, 52, 143, 178, 58, 98, 153, 29, 154, 43, 102, 59, 142, 236, 46, 247, 194, 83, 217, 128, 141, 11, 76, 90, 210, 241, 61, 253, 148, 2, 17, 0, 0, 0, 1, 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