Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5b2c235ecb92dbe6ee82089911a3576f174123d4ef074d6147ad84a130bf349

Tx prefix hash: 8a44deca4d4f79302dbb738b1155ba6897a8b4c17cdf8ee069e0a2e9cf0c52a5
Tx public key: b1b0aa1a462736dfa5a667382d348832c46cec3369d9d75300af7650f78cdeab
Timestamp: 1706303403 Timestamp [UCT]: 2024-01-26 21:10:03 Age [y:d:h:m:s]: 01:030:08:57:18
Block: 943976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282761 RingCT/type: yes/0
Extra: 01b1b0aa1a462736dfa5a667382d348832c46cec3369d9d75300af7650f78cdeab02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f3a8ba28644f9fa11b3c285b5f7bc08b1dd67e781ac440ef82c636f3d03051 0.600000000000 1402202 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": 943986, "vin": [ { "gen": { "height": 943976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f3a8ba28644f9fa11b3c285b5f7bc08b1dd67e781ac440ef82c636f3d03051" } } ], "extra": [ 1, 177, 176, 170, 26, 70, 39, 54, 223, 165, 166, 103, 56, 45, 52, 136, 50, 196, 108, 236, 51, 105, 217, 215, 83, 0, 175, 118, 80, 247, 140, 222, 171, 2, 17, 0, 0, 0, 9, 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