Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 658150004db1f09d05ed4a619e60b525a1507f70401b5aeeaf0bc0fef4cf007e

Tx prefix hash: e8a4985694281d91af6206e3e236abf74d7ff6bdf49f8d234eefa77dbf46e6da
Tx public key: d17377cda9b0360074a9697e61f624a8678b59dab40a312d94c9e9139b520342
Timestamp: 1720995729 Timestamp [UCT]: 2024-07-14 22:22:09 Age [y:d:h:m:s]: 00:222:15:01:19
Block: 1065822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158989 RingCT/type: yes/0
Extra: 01d17377cda9b0360074a9697e61f624a8678b59dab40a312d94c9e9139b52034202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1684a2649f1c0d2d94d5aae570d1339d2db53b5b2475404a93e5fdaf170b75f 0.600000000000 1536377 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": 1065832, "vin": [ { "gen": { "height": 1065822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1684a2649f1c0d2d94d5aae570d1339d2db53b5b2475404a93e5fdaf170b75f" } } ], "extra": [ 1, 209, 115, 119, 205, 169, 176, 54, 0, 116, 169, 105, 126, 97, 246, 36, 168, 103, 139, 89, 218, 180, 10, 49, 45, 148, 201, 233, 19, 155, 82, 3, 66, 2, 17, 0, 0, 0, 4, 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