Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ada86db3d97d3dfaa61682281527ac58a9d77804425f1b79210b4167c5d276

Tx prefix hash: 9ad0936bbe6d24c1149ffde98db6cff4ff9bd4a206c0edac889cffb96a1bf9bd
Tx public key: 4285cc9165d3d6e0da6b0b6c2cad5d3defe2b413ca37102bf1d3ea5cd24066cb
Timestamp: 1710734070 Timestamp [UCT]: 2024-03-18 03:54:30 Age [y:d:h:m:s]: 01:002:23:46:03
Block: 980755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263114 RingCT/type: yes/0
Extra: 014285cc9165d3d6e0da6b0b6c2cad5d3defe2b413ca37102bf1d3ea5cd24066cb02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f64f053f1cf643912e5880acfc0267b7de0ff3aad53a64099bfd7885a2072c77 0.600000000000 1440836 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": 980765, "vin": [ { "gen": { "height": 980755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f64f053f1cf643912e5880acfc0267b7de0ff3aad53a64099bfd7885a2072c77" } } ], "extra": [ 1, 66, 133, 204, 145, 101, 211, 214, 224, 218, 107, 11, 108, 44, 173, 93, 61, 239, 226, 180, 19, 202, 55, 16, 43, 241, 211, 234, 92, 210, 64, 102, 203, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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