Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71186207a7bb3b58286c9419fe666ae4435efc499fb7e1087d3b5e019ab0dc2e

Tx prefix hash: daa0196b499601449568edc00d30c7b359c773bc77c2ac7c55fb3edcdfc7aac1
Tx public key: 76e84ffb07a6c6fe5efb6a65512ee785132e102af11d3c4846dae12f5c0e592c
Timestamp: 1728872027 Timestamp [UCT]: 2024-10-14 02:13:47 Age [y:d:h:m:s]: 00:004:12:13:36
Block: 1131108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3234 RingCT/type: yes/0
Extra: 0176e84ffb07a6c6fe5efb6a65512ee785132e102af11d3c4846dae12f5c0e592c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5c2f076ced7fe3d7cd6470c37929e4f03c41644cd368ee03d5cdd9792f162d3 0.600000000000 1613989 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": 1131118, "vin": [ { "gen": { "height": 1131108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5c2f076ced7fe3d7cd6470c37929e4f03c41644cd368ee03d5cdd9792f162d3" } } ], "extra": [ 1, 118, 232, 79, 251, 7, 166, 198, 254, 94, 251, 106, 101, 81, 46, 231, 133, 19, 46, 16, 42, 241, 29, 60, 72, 70, 218, 225, 47, 92, 14, 89, 44, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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