Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3da1a7d15234fa28b5b6f863298154ed61a2d5bd47c69893f8eb7ef1cf5be702

Tx prefix hash: 88771978117522dc46cf033abaac9a5c26550f31cb4239aeb852a512f1fbe97a
Tx public key: f946f29272c53ba6cd22bf04cd289c8ef40283a4ea420dd0aaa4dec53e1bbc01
Timestamp: 1685562520 Timestamp [UCT]: 2023-05-31 19:48:40 Age [y:d:h:m:s]: 02:012:18:01:53
Block: 772297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531181 RingCT/type: yes/0
Extra: 01f946f29272c53ba6cd22bf04cd289c8ef40283a4ea420dd0aaa4dec53e1bbc0102110000000375e3f0e9000000000000000000

1 output(s) for total of 1.694570391000 dcy

stealth address amount amount idx
00: 23e65d1cd5fb0bb1373a733bdd074a2e95f286e87dbe1c7c37ffa1efcc860143 1.694570391000 1221692 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": 772307, "vin": [ { "gen": { "height": 772297 } } ], "vout": [ { "amount": 1694570391, "target": { "key": "23e65d1cd5fb0bb1373a733bdd074a2e95f286e87dbe1c7c37ffa1efcc860143" } } ], "extra": [ 1, 249, 70, 242, 146, 114, 197, 59, 166, 205, 34, 191, 4, 205, 40, 156, 142, 244, 2, 131, 164, 234, 66, 13, 208, 170, 164, 222, 197, 62, 27, 188, 1, 2, 17, 0, 0, 0, 3, 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