Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b650c7981f1c5a3c8a7e0fceb0630159a9ccfb352680868bb166ab0fc968171d

Tx prefix hash: d70319e4ebb60f493302412f3ca3c61cd371f615bff75da773fe6d55ff8503df
Tx public key: 2a9461f89e17628bcde6e155ed5aed9bdef3c0f1bda0726b7617c452b8ec1ee9
Timestamp: 1705107244 Timestamp [UCT]: 2024-01-13 00:54:04 Age [y:d:h:m:s]: 01:013:20:42:41
Block: 934069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271199 RingCT/type: yes/0
Extra: 012a9461f89e17628bcde6e155ed5aed9bdef3c0f1bda0726b7617c452b8ec1ee902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 313a3b01db3112c2614d6b9787d5224054b516d2a8cab430f9e98913c59c1f2d 0.600000000000 1392055 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": 934079, "vin": [ { "gen": { "height": 934069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "313a3b01db3112c2614d6b9787d5224054b516d2a8cab430f9e98913c59c1f2d" } } ], "extra": [ 1, 42, 148, 97, 248, 158, 23, 98, 139, 205, 230, 225, 85, 237, 90, 237, 155, 222, 243, 192, 241, 189, 160, 114, 107, 118, 23, 196, 82, 184, 236, 30, 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