Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 742684e738addbc4845e3c9894340e14d2bfdb0610ff764143840ad8f4d1f148

Tx prefix hash: f1d287b33379b993e3f86c4e3cf6e3e0d99c7315e727bfe461a925522d5b94f4
Tx public key: 9b031ebb4e0f9393971fee064d87ed21080a9ee5294ac03a93da82f4e44a80f9
Timestamp: 1733830614 Timestamp [UCT]: 2024-12-10 11:36:54 Age [y:d:h:m:s]: 00:107:14:09:49
Block: 1172124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76680 RingCT/type: yes/0
Extra: 019b031ebb4e0f9393971fee064d87ed21080a9ee5294ac03a93da82f4e44a80f9021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f185f79ef10aef1a9b375393f97aaba5d3e2c1f001267d6ac5bdcedf3f106c 0.600000000000 1657975 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": 1172134, "vin": [ { "gen": { "height": 1172124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f185f79ef10aef1a9b375393f97aaba5d3e2c1f001267d6ac5bdcedf3f106c" } } ], "extra": [ 1, 155, 3, 30, 187, 78, 15, 147, 147, 151, 31, 238, 6, 77, 135, 237, 33, 8, 10, 158, 229, 41, 74, 192, 58, 147, 218, 130, 244, 228, 74, 128, 249, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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