Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feb074b4c31990a4289dec23ecc5263d8d3a721c1cfc0ce0a4188f4466b76319

Tx prefix hash: 7f2d1e39152f68ea515b7571d1d137f2e8618f3d822afb66cf42887cbafddce1
Tx public key: 1b0990b4c963c40bc0772bbe0e91a5881fcb2f91e6a6b85887c6701955fc5241
Timestamp: 1704400177 Timestamp [UCT]: 2024-01-04 20:29:37 Age [y:d:h:m:s]: 01:152:01:06:53
Block: 928205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369839 RingCT/type: yes/0
Extra: 011b0990b4c963c40bc0772bbe0e91a5881fcb2f91e6a6b85887c6701955fc52410211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70bbc6e15d47295d9185fdc518e994438cc4d29c4f9501cc0a97e68d2c98bfc4 0.600000000000 1386063 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": 928215, "vin": [ { "gen": { "height": 928205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70bbc6e15d47295d9185fdc518e994438cc4d29c4f9501cc0a97e68d2c98bfc4" } } ], "extra": [ 1, 27, 9, 144, 180, 201, 99, 196, 11, 192, 119, 43, 190, 14, 145, 165, 136, 31, 203, 47, 145, 230, 166, 184, 88, 135, 198, 112, 25, 85, 252, 82, 65, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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