Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc50958a8198c19bbe4c346b3f89d1557192902abf58c4c2d75bbf5cb1e7f692

Tx prefix hash: d96f0f70dc471bd4b4c95a4534f2bc2b5136b3ee82e40404448ea7d7224d1a1b
Tx public key: ce3be9f66487436b54d1eac6d95fb515769345b667c0ba5ee29fe51a63bc235d
Timestamp: 1640995491 Timestamp [UCT]: 2022-01-01 00:04:51 Age [y:d:h:m:s]: 03:308:09:16:35
Block: 407790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 996908 RingCT/type: yes/0
Extra: 01ce3be9f66487436b54d1eac6d95fb515769345b667c0ba5ee29fe51a63bc235d021100000012edb0d4a3000000000000000000

1 output(s) for total of 27.341528414000 dcy

stealth address amount amount idx
00: 79d439ee4a5576a4b4dba84e7cfc29a8a8064c6d9607820c9b6b2d68e93eaf44 27.341528414000 809469 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": 407800, "vin": [ { "gen": { "height": 407790 } } ], "vout": [ { "amount": 27341528414, "target": { "key": "79d439ee4a5576a4b4dba84e7cfc29a8a8064c6d9607820c9b6b2d68e93eaf44" } } ], "extra": [ 1, 206, 59, 233, 246, 100, 135, 67, 107, 84, 209, 234, 198, 217, 95, 181, 21, 118, 147, 69, 182, 103, 192, 186, 94, 226, 159, 229, 26, 99, 188, 35, 93, 2, 17, 0, 0, 0, 18, 237, 176, 212, 163, 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