Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e23974eee40e6cadfd7a021ded6f68a22a4ddeaf406c5003988b1035825f9e3

Tx prefix hash: 2b9ae20860d4efd5a86919f088e9842878667bd5147e9046ca7f65fae48a41f7
Tx public key: f3be8af669d3873528c35bc59a2049e1a9fdaa0b96b7b7352bdc81652212a597
Timestamp: 1726357114 Timestamp [UCT]: 2024-09-14 23:38:34 Age [y:d:h:m:s]: 00:070:22:47:09
Block: 1110256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50726 RingCT/type: yes/0
Extra: 01f3be8af669d3873528c35bc59a2049e1a9fdaa0b96b7b7352bdc81652212a59702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f7b405e207cea224208de41a6d405b0da871c33e41d8f36e6972cc27a5467cc 0.600000000000 1588797 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": 1110266, "vin": [ { "gen": { "height": 1110256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7b405e207cea224208de41a6d405b0da871c33e41d8f36e6972cc27a5467cc" } } ], "extra": [ 1, 243, 190, 138, 246, 105, 211, 135, 53, 40, 195, 91, 197, 154, 32, 73, 225, 169, 253, 170, 11, 150, 183, 183, 53, 43, 220, 129, 101, 34, 18, 165, 151, 2, 17, 0, 0, 0, 5, 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