Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d657178d0ced40c2831ccc07cf1eebbd22c3263263be4775e00e3d78ce8ba13

Tx prefix hash: 4d2aced6ef37ec3d59138f9a2c3d18ab29d2df1e4b83137d093d3b44629dfecb
Tx public key: a92ed79d5e82b334e70f4a6b8e37fad8974c5436c80d7e9e29c505d4f5853d1b
Timestamp: 1702138197 Timestamp [UCT]: 2023-12-09 16:09:57 Age [y:d:h:m:s]: 01:038:21:01:59
Block: 909478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289148 RingCT/type: yes/0
Extra: 01a92ed79d5e82b334e70f4a6b8e37fad8974c5436c80d7e9e29c505d4f5853d1b02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a613c31f35fbd4f2940744a215f799612625727b45462b6d328ee0f1f1248b2 0.600000000000 1366569 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": 909488, "vin": [ { "gen": { "height": 909478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a613c31f35fbd4f2940744a215f799612625727b45462b6d328ee0f1f1248b2" } } ], "extra": [ 1, 169, 46, 215, 157, 94, 130, 179, 52, 231, 15, 74, 107, 142, 55, 250, 216, 151, 76, 84, 54, 200, 13, 126, 158, 41, 197, 5, 212, 245, 133, 61, 27, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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