Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5727d6ac3940df2f61e67b712531f13d8c3e083ba927eb07ac08b1de380d4ce

Tx prefix hash: 9e558a2f9c76e2fe1a7c60c8ec1f77f4b10ce5903e68a547be14c0c05b2b7ad2
Tx public key: 69f683aa8325bd388622944636daab65710da741c85b05743f465861700eadfc
Timestamp: 1588736110 Timestamp [UCT]: 2020-05-06 03:35:10 Age [y:d:h:m:s]: 05:182:22:43:42
Block: 98905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1305571 RingCT/type: yes/0
Extra: 0169f683aa8325bd388622944636daab65710da741c85b05743f465861700eadfc02110000004b209b4bc8000000000000000000

1 output(s) for total of 288.594095304000 dcy

stealth address amount amount idx
00: 75a6859992cbbec3d66e70ecdcbf25daa33df33aa6f8bda3b75bd5c5797024bc 288.594095304000 174705 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": 98915, "vin": [ { "gen": { "height": 98905 } } ], "vout": [ { "amount": 288594095304, "target": { "key": "75a6859992cbbec3d66e70ecdcbf25daa33df33aa6f8bda3b75bd5c5797024bc" } } ], "extra": [ 1, 105, 246, 131, 170, 131, 37, 189, 56, 134, 34, 148, 70, 54, 218, 171, 101, 113, 13, 167, 65, 200, 91, 5, 116, 63, 70, 88, 97, 112, 14, 173, 252, 2, 17, 0, 0, 0, 75, 32, 155, 75, 200, 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