Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cf0d043b814e06b09dcbb1c6def5c0879c4926e23b45de98b8c7d2479689e0e

Tx prefix hash: 67050bb7401914c9d5e5208e629404e1300b5995f50c34408177243b568cbeea
Tx public key: 7727a732507f4b819f0246d418a8eb4dcc3d567187f5a6baf47e48c901a03491
Timestamp: 1673950030 Timestamp [UCT]: 2023-01-17 10:07:10 Age [y:d:h:m:s]: 01:302:16:23:47
Block: 676641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477293 RingCT/type: yes/0
Extra: 017727a732507f4b819f0246d418a8eb4dcc3d567187f5a6baf47e48c901a034910211000000038b7b6602000000000000000000

1 output(s) for total of 3.515664531000 dcy

stealth address amount amount idx
00: c90d037d2a137bd0236be475a53ee63cbb439674512905fc9c535c77b89c0bae 3.515664531000 1118362 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": 676651, "vin": [ { "gen": { "height": 676641 } } ], "vout": [ { "amount": 3515664531, "target": { "key": "c90d037d2a137bd0236be475a53ee63cbb439674512905fc9c535c77b89c0bae" } } ], "extra": [ 1, 119, 39, 167, 50, 80, 127, 75, 129, 159, 2, 70, 212, 24, 168, 235, 77, 204, 61, 86, 113, 135, 245, 166, 186, 244, 126, 72, 201, 1, 160, 52, 145, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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