Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c0fec72ab9ff6372557617da04aed7051ff47a189f48d7eb7d97c9dd97a54d9

Tx prefix hash: c0330c8877f588bed87bd65863d0fd3cc2f1c83b14c51f15b75ada1899d5b46e
Tx public key: 49455f80ac7c118ab528e9c88a6fb05a1164afa51c1786ac9e111a2ecf4da5a2
Timestamp: 1710055887 Timestamp [UCT]: 2024-03-10 07:31:27 Age [y:d:h:m:s]: 01:052:16:30:01
Block: 975125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298654 RingCT/type: yes/0
Extra: 0149455f80ac7c118ab528e9c88a6fb05a1164afa51c1786ac9e111a2ecf4da5a20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a94e6bdf0f881ef8842b8c9f8e47815a5b34aeb69577bde1803dae7a7c4e366 0.600000000000 1435096 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": 975135, "vin": [ { "gen": { "height": 975125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a94e6bdf0f881ef8842b8c9f8e47815a5b34aeb69577bde1803dae7a7c4e366" } } ], "extra": [ 1, 73, 69, 95, 128, 172, 124, 17, 138, 181, 40, 233, 200, 138, 111, 176, 90, 17, 100, 175, 165, 28, 23, 134, 172, 158, 17, 26, 46, 207, 77, 165, 162, 2, 17, 0, 0, 0, 3, 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