Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662ca9c22da6d07bbb3f203d96c8fbc36879b1b00b1a4f8ff61eb2cf73c25f67

Tx prefix hash: b3831b4de5b61fa93213cdc1752e1aad4acd0559989627c050b21bbd7ea00c37
Tx public key: b8e6116126ba3c635479fc83cf76f6a5fefa0b21e9987e7930411f19ba66e90f
Timestamp: 1723864672 Timestamp [UCT]: 2024-08-17 03:17:52 Age [y:d:h:m:s]: 00:272:10:20:29
Block: 1089600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194601 RingCT/type: yes/0
Extra: 01b8e6116126ba3c635479fc83cf76f6a5fefa0b21e9987e7930411f19ba66e90f021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd554de8fdb4c1291d26c7cead0f6b2cf0c7d3c0e327ff61cdd1f3c6dfa2bcbd 0.600000000000 1564223 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": 1089610, "vin": [ { "gen": { "height": 1089600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd554de8fdb4c1291d26c7cead0f6b2cf0c7d3c0e327ff61cdd1f3c6dfa2bcbd" } } ], "extra": [ 1, 184, 230, 17, 97, 38, 186, 60, 99, 84, 121, 252, 131, 207, 118, 246, 165, 254, 250, 11, 33, 233, 152, 126, 121, 48, 65, 31, 25, 186, 102, 233, 15, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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