Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a845fb470e706493c896459d69ef8ce0b2c3daaf30f128cec7c513338f84e1a9

Tx prefix hash: 13127d8aed91f09a229e7e1050627b1b4013902c3423a9a2064aa3abe625995e
Tx public key: 665ca46529c63b4a0074a5583e7ba9a59eb50a088a8b06454c693cd9b4867c3d
Timestamp: 1700330374 Timestamp [UCT]: 2023-11-18 17:59:34 Age [y:d:h:m:s]: 01:176:12:32:42
Block: 894483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387356 RingCT/type: yes/0
Extra: 01665ca46529c63b4a0074a5583e7ba9a59eb50a088a8b06454c693cd9b4867c3d02110000000233af99f4000000000000000000

1 output(s) for total of 0.667123893000 dcy

stealth address amount amount idx
00: f34bf460430de089d711208f828a87f4779a79dc783f1ada57bd496474c918e4 0.667123893000 1350686 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": 894493, "vin": [ { "gen": { "height": 894483 } } ], "vout": [ { "amount": 667123893, "target": { "key": "f34bf460430de089d711208f828a87f4779a79dc783f1ada57bd496474c918e4" } } ], "extra": [ 1, 102, 92, 164, 101, 41, 198, 59, 74, 0, 116, 165, 88, 62, 123, 169, 165, 158, 181, 10, 8, 138, 139, 6, 69, 76, 105, 60, 217, 180, 134, 124, 61, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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