Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5041ceee6fbc7dcc901fb5827caa3fc1ad28fbd7dcb228a8b4f4bf80da4ef1d3

Tx prefix hash: 24d3cfdcbec8ffca1cb1ae01b7c18fddf94405932e82a68f749349d4b4b67557
Tx public key: 71f5a4e38800b8168da5d1a225b4f864dc185eb57a748875c74ac2db5e1abd60
Timestamp: 1711488427 Timestamp [UCT]: 2024-03-26 21:27:07 Age [y:d:h:m:s]: 01:044:07:19:12
Block: 987016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292631 RingCT/type: yes/0
Extra: 0171f5a4e38800b8168da5d1a225b4f864dc185eb57a748875c74ac2db5e1abd6002110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907d4a6352fc7505646d78385be3c5b2255702f093b2131ef57ce8798a331ed3 0.600000000000 1447257 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": 987026, "vin": [ { "gen": { "height": 987016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907d4a6352fc7505646d78385be3c5b2255702f093b2131ef57ce8798a331ed3" } } ], "extra": [ 1, 113, 245, 164, 227, 136, 0, 184, 22, 141, 165, 209, 162, 37, 180, 248, 100, 220, 24, 94, 181, 122, 116, 136, 117, 199, 74, 194, 219, 94, 26, 189, 96, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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