Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c78552710c744b6b1359ddc7337d7e54eff24c7f1ace0ae9c18e84d859fb98d0

Tx prefix hash: 4037aa55084f9f84620b4a50945b0621177460c25dd645afc68f201ebccd6bde
Tx public key: f85b1b7f31ea393a64fadbdb0dcfa4406169d20895f8651e7d658e83db0886cf
Timestamp: 1631617202 Timestamp [UCT]: 2021-09-14 11:00:02 Age [y:d:h:m:s]: 03:241:18:56:22
Block: 333577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 948246 RingCT/type: yes/0
Extra: 01f85b1b7f31ea393a64fadbdb0dcfa4406169d20895f8651e7d658e83db0886cf02110000000da272b9cb000000000000000000

1 output(s) for total of 48.164708934000 dcy

stealth address amount amount idx
00: 339412d008b6904cb4b2a7cef4e9deabd02c87d1f6460458730a3d21881a29d0 48.164708934000 688292 of 0

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": 333587, "vin": [ { "gen": { "height": 333577 } } ], "vout": [ { "amount": 48164708934, "target": { "key": "339412d008b6904cb4b2a7cef4e9deabd02c87d1f6460458730a3d21881a29d0" } } ], "extra": [ 1, 248, 91, 27, 127, 49, 234, 57, 58, 100, 250, 219, 219, 13, 207, 164, 64, 97, 105, 210, 8, 149, 248, 101, 30, 125, 101, 142, 131, 219, 8, 134, 207, 2, 17, 0, 0, 0, 13, 162, 114, 185, 203, 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