Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9236d13474186f08ef56a849202c7d461e78c6b6fcaf71837b2a7af5e501051f

Tx prefix hash: d0bf68556d20102bffe9b802f9167d4d4036266ea13f2cefbfa4115fd5b6cca1
Tx public key: 3fc19dcaf7801abea610490644ba577bcb6915e4a41a05f9b244a92a974b735c
Timestamp: 1712809322 Timestamp [UCT]: 2024-04-11 04:22:02 Age [y:d:h:m:s]: 00:231:16:02:14
Block: 997916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165875 RingCT/type: yes/0
Extra: 013fc19dcaf7801abea610490644ba577bcb6915e4a41a05f9b244a92a974b735c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e6f4c2401abd2665fb7ae7507bd4229f27a8dc61dd2042b4aec6b8f8e87c29 0.600000000000 1458350 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": 997926, "vin": [ { "gen": { "height": 997916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e6f4c2401abd2665fb7ae7507bd4229f27a8dc61dd2042b4aec6b8f8e87c29" } } ], "extra": [ 1, 63, 193, 157, 202, 247, 128, 26, 190, 166, 16, 73, 6, 68, 186, 87, 123, 203, 105, 21, 228, 164, 26, 5, 249, 178, 68, 169, 42, 151, 75, 115, 92, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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