Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c32fbb907cbb41c3f3eecb56303559730e518d04dd816cefe9d2e818f49aa5d

Tx prefix hash: e0561bfa0b49a30b7f5519346a5d67158990f1ca62c94fac8a48f9efc9a571e4
Tx public key: 3afc2381684b6589ba09d66dd94b60edb206f74d54a959af9b45b61798a31de9
Timestamp: 1703682895 Timestamp [UCT]: 2023-12-27 13:14:55 Age [y:d:h:m:s]: 01:100:23:14:32
Block: 922283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333262 RingCT/type: yes/0
Extra: 013afc2381684b6589ba09d66dd94b60edb206f74d54a959af9b45b61798a31de902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a441a0eaa7077c8129db94ec39b8a5f209c7d029de31ca2b7648a79f3ccd6fa 0.600000000000 1379979 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": 922293, "vin": [ { "gen": { "height": 922283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a441a0eaa7077c8129db94ec39b8a5f209c7d029de31ca2b7648a79f3ccd6fa" } } ], "extra": [ 1, 58, 252, 35, 129, 104, 75, 101, 137, 186, 9, 214, 109, 217, 75, 96, 237, 178, 6, 247, 77, 84, 169, 89, 175, 155, 69, 182, 23, 152, 163, 29, 233, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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