Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b711288cac4e6d35df82ef7234f09f387ed92e8d299cf1260fa675fb902dee5

Tx prefix hash: 97d12487f91e98436f10867d3990a6e77164fa39d9ac35239c63cbb6f0018847
Tx public key: 67769518d33d31865c41baf66eaba7e1e9d273bd0f3895e139f2df99bfea0ba6
Timestamp: 1736851560 Timestamp [UCT]: 2025-01-14 10:46:00 Age [y:d:h:m:s]: 00:155:04:58:30
Block: 1197116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110630 RingCT/type: yes/0
Extra: 0167769518d33d31865c41baf66eaba7e1e9d273bd0f3895e139f2df99bfea0ba6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b581ea513941370e801ad80d0c4b48db2cba7a509db93fa95e2ff288ec8b345d 0.600000000000 1683721 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": 1197126, "vin": [ { "gen": { "height": 1197116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b581ea513941370e801ad80d0c4b48db2cba7a509db93fa95e2ff288ec8b345d" } } ], "extra": [ 1, 103, 118, 149, 24, 211, 61, 49, 134, 92, 65, 186, 246, 110, 171, 167, 225, 233, 210, 115, 189, 15, 56, 149, 225, 57, 242, 223, 153, 191, 234, 11, 166, 2, 17, 0, 0, 0, 4, 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